Skip to content

Instantly share code, notes, and snippets.

@AKCodez
AKCodez / claude-code-statusline-guide.md
Last active October 18, 2026 03:43
Claude Code Status Line - Complete Guide: all fields, config, ready-to-use scripts

Claude Code Status Line - Complete Guide: all fields, config, ready-to-use scripts

Claude Code Status Line — Complete Guide

A persistent, customizable bar at the bottom of Claude Code that shows real-time session data.

image

LLM Wiki

A pattern for building personal knowledge bases using LLMs.

This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.

The core idea

Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.

@RandalSchwartz
RandalSchwartz / 000 README.md
Last active October 18, 2026 02:56
Randal's Workflow (this week, anyway)

Randal's Preferred Ticket Resolution Workflow — Index & Series Links

📖 Companion Articles — The Synthetic Scars Series on DEV.to:

Proxmox VE tips

Just a somewhat chaotic list of personal Proxmox VE related tips/notes or interesting (to me) things I'm working on or experiment with.
Some of the things you see here are niche or purely experimental. I try to label them as such, but as always with random code snippets, make sure to review anything before running it in your own environment. Perhaps test in a virtual PVE first.

Please note that unless you see a shebang (#!/...) these code blocks are usually meant to be copy & pasted directly into the shell. Some of the steps will not work if you run part of them in a script and copy paste other ones as they rely on variables set before.
The { and } surrounding some scripts are meant to avoid cluttering your shell history with individual commands, etc. You can ignore them if you manually copy paste the individual commands.

Table of contents